Repository navigation
docs(roadmap): C-first sufficiency targets and approved v2 Issue template - #40
Merged
xLagerFeuer merged 2 commits intoNov 17, 2026
Merged
Conversation
Prioritize first-party C construction for functions without evidenced C or A, exclude already-autonomous functions from mandatory C engineering, preserve legitimate parent rights, separate P0 targets from P1 prerequisites and P2 optional modes. Adopt eight-section target/dependency/sufficiency Issue template with tests.
xLagerFeuer
deleted the
docs/c-first-roadmap-priority-v2-issue-template-20261118
branch
November 17, 2026 21:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Apply the owner's approved v2 capability integration roadmap Issue template, and make useful, evidence-backed
Csufficiency the explicit default target ofupstream roadmapfor functions without confirmedAorC.This is a roadmap-procedure and template change, not a Paperclip product implementation, a VSM Index reassessment, an external maintainer Issue or an automatic fork Issue publication.
Behavior changes
A/A(P)orC/C(P). For—, unresolved?and eligibleP, seek the smallest source-native change set that would be sufficient for a first-party developer-composableCpath when there is genuine user value. Resolve?and current-source conflicts first; preserve legitimatePauthority.A/A(P)function does not need new mandatory C work, even though the two classifications are not logical synonyms. AlreadyC/C(P)functions do not need duplicate constructors. No autonomy-grade ladder.P0= a material, source-backed C sufficiency target;P1= dependencies needed for that target, which may execute first;P2= optional modes/refinements. The choice is based on operator benefit, reusable Issues/PRs, measurable acceptance, complexity and cost—not the lowest Index grade.NEEDS_EVIDENCE/NO_USEFUL_CHANGE.Files and checks
PROTOCOL.md: default target, priority and receipt gate.docs/CAPABILITY_ROADMAP.md: target-first procedure and receipt.templates/FORK_CAPABILITY_ROADMAP_ISSUE.md: v2, Opensiro spelling.tests/test_fork_roadmap_issue_template.py: v2 sections and classification/priority/consent invariants.CHANGELOG.md: unreleased entry.No version/Release change, product branch edit or public GitHub Issue. No edit of the existing Paperclip/Browser Harness historical roadmap examples in this PR.